Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines which are not met ❌

• A patch release is not allowed to narrow the supported ranges of Julia versions. The ranges have changed from Pkg.Versions.VersionRange[VersionRange("1.6.0 - 1")] (in 1.0.0) to Pkg.Versions.VersionRange[VersionRange("1.10.0 - 1")] (in 1.0.1).

2. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

Blocking in favor of #122689.

Small question for anyone who might read this: why wasn't this pull request updated? I simply bumped the version and retriggered Registrator on that latest commit (JuliaTrustworthyAI/TaijaData.jl@d6dc1d3). I seem to remember that this approach worked for me in the past (though perhaps not when changing the package version).

Yes, if you change version number, Registrator uses a different branch name, which implies that a new PR is created. If you keep the version number (and some other data that you can't really change for a new version anyway), the same PR will be updated.